Transport for wireless radio access networks

ABSTRACT

A radio access network includes a transport network layer; a radio network layer having a layer 2 network for communicating between entities within the radio network layer by exchanging datagrams having a predetermined format used only within the radio network layer. Accordingly, the present invention provides for a true decoupling at layer 2 between the radio network layer and the transport network layer. Addressing at layer 2 can enable both connectionless and connection oriented using an overlay connectivity model. Layer 2 in the radio network layer is implemented as an Ethernet network.

FIELD OF THE INVENTION

[0001] The present invention relates to transport for wireless radioaccess networks.

BACKGROUND OF THE INVENTION

[0002]FIG. 1 illustrates a known reference model for a radio accessnetwork (RAN). A base station controller/radio network controller(BSC/RNC) 10 is coupled to a plurality of wireless base station 12, 14,16, 18 via a radio access network 20. The radio access network can bemodeled as a radio network layer (RNL) 22 and a transport network layer24 and three planes intersecting those layers, a radio network controlplane 26, a transport network control plane 28 and a user plane 30. Thenetwork may be leased from a service provider (SP) or owned by thewireless service operator.

[0003] In operation, the transport network layer (TNL) receives arequest from the RNL²² to establish a bi-directional transport bearerfor datagram traffic. The request includes the end system address andtransport bearer association received from the peer. It also includesthe quality of service and resources required from the transportnetwork. In summary it shall:

[0004] Provide unique connection identifiers such that individual flowscan be uniquely addressed for both user plane as well as control plane(eg VPI, VCI, CID in AAL2/ATM) [mandatory];

[0005] Provide in-sequence delivery of PDUs to upper layers [mandatory];

[0006] Support sending coordinated dedicated channels (DCHs) multiplexedonto the same transport bearer (i.e., frame multiplexing, e.g. AAL2/ATM)[mandatory];

[0007] Provide proper mappings of required RNL bearer channels QoS toTNL resources (eg AALx in ATM) [mandatory]

[0008] Provide transport signalling protocol used to setup and tear downtransport bearers (eg ALCAP in 3GPP r3) [mandatory];

[0009] Provide segmentation and re-assembly mechanism in order to fit tothe maximum PDU size (i.e., R3 ATM AAL2 SSSAR layer function)[mandatory]

[0010]FIG. 2 illustrates a known RAN network system model. The RANnetwork system model includes the wireless base station controller 10,the wireless base station 12 and an intervening transport network (TRAN)40. The TRAN 40 includes points of attachment (PoA) 42 and 44 andintranetwork switching collectively represented by function block 46.For the system model of FIG. 2 the current network connectivity model isa peering model. For the peering model: User traffic is “peered” withService Provider's network at point of attachment (PoA) viarudimentary/sophisticated User Network Interface (UNI). In this model,user quality of service (QoS) requirements are snooped by the SP orsignaled from user to the SP (via the UNI interface) in order to satisfyrequired QoS guarantees.

[0011] Consequently wireless datagrams need to be processed by bothwireless end points and SP TRAN equipment. This means all sub-systemsneed to have common understanding of: QoS information, Signalingcapabilities and Flow segregation ID across PoA.

[0012] The known RNL peering connectivity model imposes upon the TNL theneed to also implement a peering connection-oriented model; currentimplementations of datagram addressing are peering-like, coupling RNL 22(DCH-ID, etc) and TNL 24 (AAL2 CID, etc) identifiers.

[0013] Emerging connectionless protocols, such as IP are being proposedas the new TNL transport mechanism and will have to meetconnection-oriented requirements

[0014] In order to use connectionless IP, development of mechanisms tooffer connection-oriented capabilities to wireless TNL layer needs totake place.

SUMMARY OF THE INVENTION

[0015] An object of the present invention is to provide an improvedtransport for wireless radio access networks.

[0016] In accordance with an aspect of the present invention there isprovided a method of operating a radio access network comprising:establishing a radio network layer; establishing a transport networklayer; and communicating between entities within the radio network layerby exchanging datagrams having a predetermined format used only withinthe radio network layer.

[0017] In accordance with an aspect of the present invention there isprovided a radio access network comprising: a transport network layer; aradio network layer including a layer 2 network for communicatingbetween entities within the radio network layer by exchanging datagramshaving a predetermined format used only within the radio network layer.

[0018] Accordingly, the present invention provides for a true decouplingat layer 2 between the radio network layer and the transport networklayer.

[0019] In accordance with an aspect of the present invention a method ofprocessing layer 2 datagrams within RNL is provided that facilitatedecoupling thereof.

[0020] Addressing at layer 2 can enable both connectionless andconnection oriented using an overlay connectivity model

BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The present invention will be further understood from thefollowing detailed description with reference to the drawings in which:

[0022]FIG. 1 illustrates in a block diagram a known reference model fora radio access network (RAN);

[0023]FIG. 2 illustrates in a block diagram a known RAN system model;

[0024]FIG. 3 illustrates in a functional block diagram a wireless basestation and a base station controller communicating via a datagramservice in accordance with an embodiment of the present invention;

[0025]FIGS. 4a and 4 b illustrates in block diagrams transport optionsfor the datagram service of FIG. 3;

[0026]FIG. 5 illustrates in a block diagram the main functionalcomponents of the wireless base station and the base station controllerof FIG. 3;

[0027]FIG. 6 illustrates the functional components of the host platformswitch of FIG. 5 in further detail;

[0028]FIG. 7 illustrates Ethernet encapsulation for the datagram servicefor length encapsulation;

[0029]FIG. 8 illustrates Ethernet encapsulation for the datagram servicefor type encapsulation;

[0030]FIG. 9 illustrates in a functional block diagram second tieraddress assignment in accordance with an embodiment of the presentinvention;

[0031]FIG. 10 illustrates in a block diagram various point of attachmentoperational configurations possible using the datagram service of FIG.3; and

[0032]FIG. 11 illustrates in a block diagram how a soft hand-off ishandled using the datagram service of FIG. 3.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

[0033] Referring to FIG. 2, there is illustrated in a block diagram aknown RAN system model implemented in an overlay model in accordancewith an embodiment of the present invention.

[0034] For the overlay model: User datagram requirements are muchsimplified. The service provider (SP) offers quality of service (QoS)guarantees as part of the service in a point-to-point orpoint-to-multipoint (via Dedicated or Virtual Private Line serviceframework). Hence, the user datagram does not need to carry any flowsegregation ID peering with SP, nor does it need to offer any signalingcapability, nor any QoS information as the service leased corresponds tocommon denominator user flows characteristics, i.e. highest QoS.

[0035] Consequently, datagrams processed by wireless can be totallyindependent from SP TRAN datagram processing functions enabled via PoAedge translation (physical port-based mapping): This means each point ofattachment (PoA) 42 and 44 provides an operational independence of: QoS,signaling and flow segregation technologies.

[0036] The wireless base station controller 10 and wireless base station12 include wireless radio frames computing platforms. Host systemsintercommunicating using either L2 frames or L3 packets as datagrams.

[0037] The network points of attachment (POA) 42 and 44 either mapwireless datagrams into lower layer transport services (examples:DSx,STSx, OCs for dedicated PL) or actively switches the datagrams(examples: Ethernet Switching, MPLS, IP routing for virtual PL)

[0038] The transport provided by the TRAN 40, as represented by a pipe48 provides physical port-based, point-to-point flow of datagrams overdedicated or virtual Ethernet private line sessions with a specificservice level agreement (SLA).

[0039] Intra-switches as represented by the block 46 provides backhaulnetworking intra-switching (examples are: TDM switched, SONET/SDH Ringor Meshed networks).

[0040] The cellular terrestrial radio access network (TRAN) 40,typically uses private addressing space (examples, A/Z PL, IPV4/6,Ethernet Mac).

[0041] Referring to FIG. 3, there is illustrated in a functional blockdiagram a wireless base station and a base station controllercommunicating via a datagram service in accordance with an embodiment ofthe present invention. The base station function block 12′ includes aradio frequency domain 50, a digital domain 52 and a datagram service54. The base station controller function block 10′ includes a mobilityfunction 60, a packet processing function 62, a wireless applicationcore steering 64 and a datagram service 66. A datagram is anindependent, self-contained message sent over the network whose arrival,arrival time, and content integrity guarantees are assured by networkservice and not by the datagram protocol capabilities. Datagrams can beeither wireless radio frames or OA&M signals.

[0042] Referring to FIGS. 4a and 4 b, there are illustrated in blockdiagrams transport options for the datagram service of FIG. 3. Behindthe POA-edge (42 and 44), once the traffic is encapsulated, the carrieris free to use the most economic L1, L2, L3 switching fabric thatprovides desired SLA. The embodiments of the present invention are basedon an overlay network system design, enabling carrier providers tooperate TRAN (40) networks independent of wireless operator's equipment(10 & 12). FIG. 4a illustrates how a carrier frame 80 having an embeddedEthernet frame 82 can be transported using sonnet 84 as payload 86 oroptical channels 88 as payload 90. FIG. 4b illustrates how carrier frame94 and Ethernet frame 96 are combined to form a frame 97, where the 2optical Ethernet label 98 includes an Ethernet MAC adding 100 and wherethe optical Ethernet MPLS label 102 includes the Ethernet MAC address104.

[0043] Referring to FIG. 5, there is illustrated in a block diagram themain hardware components of the wireless base station and the basestation controller of FIG. 3.

[0044] The base station 12 includes a host platform switch 110, aplurality of process modules 111 each having a plurality of applicationprocesses (AP) 112. Similarly the base station controller 10 includes ahost platform switch 120, a plurality of process modules 121 each havinga plurality of application processes (AP) 122.

[0045] The application processes include radio modems, RLC & RRL S/W.Radio PDU may or may not contain AP-ID information for necessary forflow steering function performed at PM level 111 and 121 (second tieraddress options)

[0046] Each process module 112, 122 has a single Ethernet MAC address(OUI=0). A simple packet steering function is performed by the PM 112,122 in order to send PDU to individual AP 112, 122 (2 second tieraddress options)

[0047] Host platform switches 110 and 120 are Ethernet switching pointsthat do not possess Ethernet MAC addresses (except for OAM&P agent, etc)as it performs layer-2 bridging algorithm. A direct 1:1 PM address andHost Switch port mapping is used for design simplicity.

[0048] For dedicated Ethernet private line the inter-host frame walkthrough is as follows: AP 112, 122 are identified by STA (second tieraddress). PM 111, 121 have a single Ethernet MAC address. PM framesteering function is based on STA information.

[0049] There is simple 1:1 relationship between Host Switch 110, 120port and PM 112, 122 MAC address. Host switches frames based on FTAaddress information (i.e. Ethernet DA and SA) where a forwardingdecision is based on destination address (DA) MAC/egress Port andlearning tables that are populated via secondary addresses (SA)MAC/ingress Port information;

[0050] Host Switch 110 forwards frames to PoA 44 using PM DA MAC addressinformation. TNL 40 simply encapsulates user flow with no regard of useraddress/QoS information as service is offered on dedicated port basis(non shared). Private Ethernet addressing space enables wirelessoperator to assign any type of networking identifier (examples: URL, IP,MPLS/LSP, ATM VP/VC, L2 Macs).

[0051] The overlay TNL network 40 point of attachment 40, 44 forwardingis based on dedicated physical or virtual port mapping (examples DSx,STSx, LSP).

[0052] AP 112, 122 addresses are mapped to Ethernet FTA& STA addressspace. Ethernet FTA can be learned or manually provisioned at AP driverinterface. If automatically provisioned, Ethernet DA MAC addresses canutilize standard registration protocol (ie GARP, GVRP, or even othersimpler methods).

[0053] The simple method referred here aims at leveraging the simple802.1D bridging algorithm where MAC addresses are learned and aged outas a fundamental behaviour that can be exploited for end-host EthernetMAC address discovery and thus simplify tremendously the softwareinvestment on each nodal system to perform such a task at boot time. Thehighlights are as follows:

[0054] 1) end host (e.g. BTS) that needs to discover the other endhost(s) (e.g. BSC/RNC) can simply issue from the AP a speciallyVLAN-tagged broadcast packet to network (e.g. backhaul).

[0055] 2) This special VLAN-tagged broadcast (or VLAN-containedbroadcast) restricts ENET pollution to only VLAN-aware switches andregistered end-host MAC station. It also requires all ENET switch alongthe path to be VLAN-capable.

[0056] 3) Once the other host receives that special VLAN-taggedbroadcast frame, it responds by issuing a Unicast back to the sender.

[0057] 4) Once sender receives the unicast frame, the process is over asboth end hosts now has both respective destination MAC address forremaining of datagram exchange.

[0058] Inter-Host Frame Walkthrough Over EPL Service Framework:

[0059] AP<-> PM

[0060] APs are identified by STA 148 (second tier address). PM havesingle Ethernet MAC address. PM datagram steering function performed byhost switch is based on FTA information 146.

[0061] PM <-> Host

[0062] There is simple 1:1 relationship between Host Switch port and PMMAC address. Host switches frames based on FTA address information whereforwarding decision is based on DA MAC/egress Port and learning tablesare populated via SA MAC/ingress Port information;

[0063] Host <-> PoA

[0064] Host Switch 110 forwards frames to PoA 44 using PM 110 DA MACaddress information 146. TNL 40 simply encapsulates user flow with noregard of user address/QoS information as service is offered ondedicated port basis (non shared). Private Ethernet addressing spaceenables wireless operator to assign any type of networking identifier(examples: URL, IP, MPLS/LSP, VLAN tags, L2 Macs).

[0065] TNL Overlay

[0066] TNL 40 Network point of attachment forwarding based on dedicatedphysical or virtual port mapping (examples Label insertion, MPLS-like,Martini, etc). QoS traffic management is implemented based on queuingmodel where statistical multiplexing is possible.

[0067] End Points Address Determination

[0068] AP addresses are mapped to Ethernet FTA& STA address space (seeFIGS. 7 & 8). Ethernet FTA can be learned or manually provisioned at APdriver interface. If automatically provisioned, Ethernet DA MACaddresses can utilize standard registration protocol (i.e. GARP, GVRP,or even other simpler methods) as described herein above.

[0069] Referring to FIG. 6 shows functional components of the hostplatform switch of FIG. 5 in further detail. The host platform switchhas an Ethernet address, a bearer function 130 which performs the 802.1Dforwarding algorithm, and a control function 132 which requires anEthernet & IP addresses to terminate host management house keepingtasks. Binding of Host Ethernet address with higher host-levelprovisioned address, such as IP address or URLs, can be accomplished byARP or DHCP-like procedures.

[0070] Referring to FIG. 7, there is illustrated ethernet encapsulationfor the datagram service for length encapsulation. Wireless datagramsfor Mobile customer traffic (examples: direct radio frames (RFP) orRFP/AAL2/ATM or RFP/BCN, etc), as well as wireless host IP OA&M &control datagrams are encapsulated as Ethernet payloads 144.

[0071] One or many wireless datagrams can be encapsulated (coordinatedDCHs over single transport bearer*)

[0072] For 802.3 Ethernet Length Encapsulation the first tier address146 includes 12 Bytes (2×48-bit) Destination & Source MAC are used asfirst tier address (FTA) 146, and a second tier address 148 (STA) thatis 8 Bytes total that contains a fixed LLC Header 150 [(3B) (DSAP=0xAA,SSAP=0xAA, Ctrl=0x3)] & SNAP Header 152 (5B) available for second tieraddress. The SNAP header 152 contains SNAP OUI (3B) and SNAP Pid (2B).

[0073] Intra-Host Ethernet Length STA Walk Through:

[0074] Host <-> PM

[0075] There is 1:1 relationship between Host Switch port and PM MACaddress. Host switches frames based on FTA address information 146 whereforwarding decision is based on DA MAC/egress Port and learning tablesare populated via SA MAC/ingress Port information.

[0076] PM <-> Host

[0077] APs are identified by STA (148 second tier address). PM havesingle Ethernet MAC address. PM frame steering function is based on STASNAP Header address 152 information, (i.e. fixed LLC header 150 fixed toDSAP=0xAA, SSAP=0xAA, Ctrl=0x03+SNAP header (5B-152). When using theLength encapsulation, the 2 bytes 154 following the SA field representthe actual length of data payload. The LLC being fixed, the SNAP OUI &SNAP Pid can be used (Pid=2 ¹⁶ available address space) to addresshigher-layer protocol (e.g. application).

[0078] Referring to FIG. 8, there is illustrated Ethernet encapsulationfor the datagram service for type encapsulation.

[0079] 802.3 Ethernet Type Encapsulation:

[0080] 12 Bytes Destination & Source MAC are used as first tier address(FTA)

[0081] 4 Bytes VLAN tags (VPID & TCI) are available for second tieraddress (STA)

[0082] Intra-Host Ethernet Type STA Walkthrough

[0083] Host <-> PM

[0084] There is 1:1 relationship between Host Switch port and PM MACaddress. Host switches frames based on FTA address information 146 whereforwarding decision is based on DA MAC/egress Port and learning tablesare populated via SA MAC/ingress Port information;

[0085] PM <-> Host

[0086] APs are identified by STA (160 second tier address). PM havesingle Ethernet MAC address. PM frame steering function is based on STA802.1Q VLAN tag information 160. When using the Type encapsulation, the2 bytes 162 following the SA field identifies the nature of the clientprotocol running above Ethernet (e.g. IP uses Type field=0x0800). APidentification and steering is done via Tag Control Information (TCI)164 field which contains 3-bits for QoS priority, 1 bit for control andremaining 12 bits for VLAN-ID, thus 2¹²=4096 available addressable spaceto address higher-layer protocol (e.g. applications).

[0087] Referring to FIG. 9, there is illustrated in a functional blockdiagram second tier address assignment in accordance with an embodimentof the present invention

[0088] A mobile terminal user entity 200 having an application layer 202and an L2 204 becomes associated with a base station 12 having a radionetwork layer 22 RNL MAC layer 206. The RNL MAC layer 206 needs to bebound to the Ethernet 208, which makes use of a L1 wrapper 210.

[0089] For second tier address (STA) assignment there are three possiblemethods. Endpoints for end-to-end datagram communication are uniquelyidentified by FTA and STA. STA can be assigned by a manual 212, learning214 or connection oriented 216 procedures. RNL link setup signaling canbe used to manage Host & Port address, that is, from an architecturalperspective one does not have to rely on the existence of UDP/IP stack

[0090] Referring to FIG. 10, there is illustrated in a block diagramvarious point of attachment operational configurations possible usingthe datagram service of FIG. 3.

[0091] POA Operational Configurations—Dedicated-PtPt & Groomed-PtMP

[0092]224 One POA 44 is connected to only one BTS 12, with one portappearance on the BTS 12 HPS 110. This is applicable to bothconfigurations 220 and 230.

[0093]220 One POA 42 port appearance on BSC 10 HPS 20 for each BTS 12.

[0094]236 One POA 44 connected to more than one BTS 12, with one portappearance on each BTS HPS 10. This is applicable to both configurations220 and 230.

[0095]230 One POA 42 is connected to only one BSC 10, with one portappearance on BSC HPS 20 for more than one BTS 12.

[0096] POA Interface Addressing & Management

[0097] For 22, 236 all TRAN traffic passing through the POA 228, 238 issteered to the customer facing port (BTS 12 or BSC 10). All Ethernetfirst tiered addresses 146 receive the same steering treatment to thecustomer port. Second tiered addresses are not processed by the POA. Thesteering function is manually provisioned at startup and does notchange.

[0098] For 220, all TRAN traffic passing through the POA 222 is steeredto the corresponding BTS based on Ethernet first tiered addresses 146.Second tiered addresses are not processed by the POA.

[0099] Steering function is manually provisioned or realized through anEthernet learned/auto discovery process, as described with regard toFIG. 2.

[0100] Optional UNI signaled be applied for all BTS groomed traffic(logical channels) flowing over the high speed medium using secondtiered addresses.

[0101] Embodiments of the present invention embrace an overlay modelthat enables TRAN POA-to-POA addressing to be independent from wirelessequipment addressing. Addressing within the TRAN can be accomplished twodifferent ways:

[0102] A dedicated Ethernet Private line tunnel where the TRAN network40 is used to tunnel traffic between two POAs 42 and 44.

[0103] A Virtual Ethernet switched service where the TRAN network 40operates like a distributed Ethernet switch between POAs 42 and 44.

[0104] In both cases the TRAN wireless traffic is encapsulated using anyLayer 1, Layer 2, or Layer 3 networking scheme. Embodiments of thepresent invention described herein have emphasized an all Ethernet layer2 approach, however the architecture foundation of the all Ethernetapproach does not exclude encapsulating Ethernet frames at POAs 42 and44 using either IP or SONET techniques. TRAN addressing scheme betweenPOA can be any techniques; using one or both FTA and STAs methods. Theonly requirement is that TRAN FTA and STAs remain independent ofencapsulated wireless equipment FTA and STAs.

[0105] Referring to FIG. 11, there is illustrated in a block diagram howa soft hand-off is handled using the datagram service of FIG. 3. Forsimplicity the TRAN 40 is represented by an Ethernet switch 46. Theprocess for a downlink TNL multicast (Soft Hand-Off) is illustrated.

[0106] Today's RNL (RLC, etc) needs to perform packet duplication whilein soft hand off mode.

[0107] An Ethernet-switched TNL offers integrated multicast capabilitieswhere only objects needs to be exchanged between the BSC 10 and BTS 10and BTS 12 (DCH_(source), BTS-ID₁, BTS-ID_(n), Event-ID).

[0108] If the Type STA option of FIG. 7 is used two methods is possible:

[0109] GARP signaling events triggered at power measurement messagespassing a threshold value invoking soft-hand off operation of drift-BTS14. This results in GARP registration exchange for all BTS participatingin soft-hand off operation. GARP tear-down triggered by powermeasurement going below a threshold forcing to leave multicast. Thismethod needs the creation of new GARP multicast address specific forwireless multicast soft hand-off application.

[0110] Use VLAN registration during soft hand off scenario wherecontained frame broadcast is performed inside VLAN paths only(VLAN-contained broadcast). Here GVRP is used as part ofregistration/removal exchange.

[0111] Glossary

[0112] AP=wireless application process. That's usually physicallyinstantiated at silicon/silicon island level but abstraction boundarycan be extended up to board packaging level.

[0113] PM=Process Module. Includes many AP processes. Typicallyphysically instantiated at the board level but abstraction boundary canbe extended up to shelves and frame packaging level.

[0114] Host=Platform addressable entity. Include several PMs. Typicallyphysically instantiated at the shelf level but abstraction boundary canbe extended up to set of shelves and/or frame packaging level.

[0115] Frame=layer 2 protocol information definition (eg ATM, Ethernet,FR, PPP, etc). Data link addressing visibility and link error detectiondone on a per hop/segment basis;

[0116] Packet=Layer 3 protocol information definition (eg IP, IPX, etc).Network layer where addressing visibility is beyond hop/segment subnet.

[0117] STA=Second Tier Address component

[0118] FTA=First Tier Address component

[0119] RFP=Radio Frame Protocol

[0120] ALCAP=Generic name for the transport signalling protocols used toset-up and tear-down transport bearers

[0121] EPL=Ethernet Private Line service;

[0122] D-EPL=Dedicated Ethernet Private Line service. Not statisticalmultiplexing occurs and usually maps onto dedicated circuits (egDSx/STx, etc);

[0123] V-EPL=Virtual Ethernet Private Line service. Statisticalmultiplexing benefits exists applying QoS traffic management principlesover queuing model;

[0124] HPS=Host Platform Switch.

What is claimed is:
 1. A method of operating a radio access networkcomprising: establishing a radio network layer; establishing a transportnetwork layer; and communicating between entities within the radionetwork layer by exchanging datagrams having a predetermined format usedonly within the radio network layer.
 2. A method as claimed in claim 1wherein the datagram comprises an Ethernet packet.
 3. A method asclaimed in claim 2 wherein the Ethernet packet includes a first tieraddress.
 4. A method as claimed in claim 2 wherein the Ethernet packetincludes a second tier address.
 5. A method as claimed in claim 4wherein the second tier address includes length.
 6. A method as claimedin claim 5 wherein the second tier address includes an LLC header.
 7. Amethod as claimed in claim 5 wherein the second tier address includes aSNAP header.
 8. A method as claimed in claim 4 wherein the second tieraddress includes type.
 9. A method as claimed in claim 8 wherein thesecond tier address includes a VLAN tag.
 10. A method as claimed inclaim 1 wherein the radio network layer includes and Ethernet network.11. A method as claimed in claim 10 wherein the step of establishing theradio network layer includes the step of binding the radio network layermedia access codes (MAC) to addresses for the. Ethernet network.
 12. Amethod as claimed in claim 11 wherein the step of binding includesmanual end point provisioning.
 13. A method as claimed in claim 11wherein the step of binding includes connectionless learning by theEthernet network first flooding the network and then using a unicastlearning procedure.
 14. A method as claimed in claim 11 wherein the stepof binding includes establisng sockets on a point-to-point basis.
 15. Aradio access network comprising: a transport network layer; a radionetwork layer including a layer 2 network for communicating betweenentities within the radio network layer by exchanging datagrams having apredetermined format used only within the radio network layer.
 16. Anetwork as claimed in claim 15 wherein the datagram comprises anEthernet packet.
 17. A network as claimed in claim 16 wherein theEthernet packet includes a first tier address.
 18. A network as claimedin claim 16 wherein the Ethernet packet includes a second tier address.19. A network as claimed in claim 18 wherein the second tier addressincludes length.
 20. A network as claimed in claim 19 wherein the secondtier address includes an LLC header.
 21. A network as claimed in claim19 wherein the second tier address includes a SNAP header.
 22. A networkas claimed in claim 18 wherein the second tier address includes type.23. A network as claimed in claim 22 wherein the second tier addressincludes a VLAN tag.
 24. A network as claimed in claim 15 wherein theradio network layer includes and Ethernet network.
 25. A network asclaimed in claim 24 wherein the step of establishing the radio networklayer includes the step of binding the radio network layer media accesscodes (MAC) to addresses for the Ethernet network.
 26. A network asclaimed in claim 25 wherein the step of binding includes manual endpoint provisioning.
 27. A network as claimed in claim 25 wherein thestep of binding includes connectionless learning by the Ethernet networkfirst flooding the network and then using a unicast learning procedure.28. A network as claimed in claim 25 wherein the step of bindingincludes establing sockets on a point-to-point basis.